Skip to content

chore(deps): Bump actions/setup-node from 4 to 6#7

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-node-6
Open

chore(deps): Bump actions/setup-node from 4 to 6#7
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-node-6

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 24, 2026

Bumps actions/setup-node from 4 to 6.

Release notes

Sourced from actions/setup-node's releases.

v6.0.0

What's Changed

Breaking Changes

Dependency Upgrades

Full Changelog: actions/setup-node@v5...v6.0.0

v5.0.0

What's Changed

Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless. To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades

New Contributors

Full Changelog: actions/setup-node@v4...v5.0.0

v4.4.0

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4...v6)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels May 24, 2026
xuyushun441-sys pushed a commit that referenced this pull request May 25, 2026
New template @template/helpdesk (port 4006) — a customer support / ticketing
template where AI fields are first-class schema citizens, not bolted-on macros.

Differentiation vs Zendesk / Freshdesk / Intercom:
- AI fields native on the ticket object (ai_summary / ai_category / ai_intent /
  ai_sentiment / ai_priority_suggestion / ai_language / ai_suggested_reply /
  ai_suggested_kb_ids / ai_confidence / ai_triage_at) — populated by a stub
  flow you replace with your LLM of choice. README documents the swap.
- Tri-lingual i18n (en + zh-CN) out of the box.
- Customer portal is just another permission profile on the same platform —
  no upcharge.
- Full SQL access to all support data; no vendor lock-in.

Contents:
- 6 objects: ticket, customer, team, message, kb_article, sla_policy
- 2 state machines: ticket (new→triaged→in_progress→waiting_customer→
  resolved→closed + escalated branch) and kb_article (draft→review→
  published→archived)
- 5 flows: ai_triage_on_create (LLM hook stub), sla_first_response_warn,
  sla_resolution_breach, auto_close_resolved, escalate_angry_customer
- 2 dashboards: agent_workbench + manager_overview
- 3 profiles: helpdesk_admin / agent / customer_portal
- Seed data: 3 teams, 4 SLA policies, 6 customers, 6 KB articles,
  9 tickets covering every status & sentiment incl. escalated/angry/breaching
- README + CHARTER (CHARTER documents why we exceed the 4-object convention)

CHARTER deviation: 6 objects (vs convention of 4) — justified because a
credible support model needs threaded messages + KB + SLA as separate
objects, not as fields. Documented in CHARTER.md.

Platform gaps that affect this template are cataloged in
framework/docs/PLATFORM_GAPS_FROM_TEMPLATES.md and called out in the
template README (notification delivery #1, CEL date helpers #7, slotted
page regions #8, dashboard chart aggregation #10).

Verified: typecheck clean, build clean (6 objects, 75 fields, 1 app,
6 views, 1 page, 2 dashboards, 5 flows, 4 roles, 3 permissions, 157KB
artifact), dev server boots on :4006, browser smoke test confirms
dashboards render, ticket list + detail page work, lookups + enum
labels + i18n all resolve correctly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants